[Snyk] Security upgrade @backstage/plugin-azure-devops-common from 0.0.0-use.local to 0.0.1#5627
[Snyk] Security upgrade @backstage/plugin-azure-devops-common from 0.0.0-use.local to 0.0.1#5627snyk-io[bot] wants to merge 1 commit intomasterfrom
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-WEBPACKDEVSERVER-10300775 - https://snyk.io/vuln/SNYK-JS-TARFS-10293725 - https://snyk.io/vuln/SNYK-JS-WEBPACKDEVSERVER-10300777
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Reviewer's GuideThis PR bumps the @backstage/plugin-azure-devops-common dependency from a workspace reference to version 0.0.1 in plugins/azure-devops/package.json to resolve several high- and medium-severity security vulnerabilities; it also highlights the need to regenerate the yarn.lock file. Sequence Diagram: Snyk PR Creation and Developer HandlingsequenceDiagram
actor Snyk
participant GitHubRepo as "GitHub Repository"
actor Developer
Snyk->>GitHubRepo: Scan project for vulnerabilities
GitHubRepo-->>Snyk: Report: "@backstage/plugin-azure-devops-common" vulnerable
Snyk->>GitHubRepo: Create PR: Upgrade "@backstage/plugin-azure-devops-common" to 0.0.1
Developer->>GitHubRepo: Review PR
Developer->>Developer: Manually update yarn.lock (as per PR warning)
Developer->>Developer: Run `yarn` (for zero-installs users, if applicable)
Developer->>GitHubRepo: Test changes (e.g., local build, CI)
Developer->>GitHubRepo: Merge PR
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| "@backstage/core-plugin-api": "workspace:^", | ||
| "@backstage/errors": "workspace:^", | ||
| "@backstage/plugin-azure-devops-common": "workspace:^", | ||
| "@backstage/plugin-azure-devops-common": "0.0.1", |
There was a problem hiding this comment.
The PR is missing the updated yarn.lock file, which is required to actually fix the security vulnerabilities. Without updating the lockfile, changing the version in package.json alone won't resolve the vulnerabilities when the project is built.
As noted in the PR description warning, the yarn.lock file needs to be updated manually before merging. Please run yarn to generate the updated lockfile and include it in this PR.
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
Snyk has created this PR to fix 3 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/azure-devops/package.jsonNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-WEBPACKDEVSERVER-10300775
SNYK-JS-TARFS-10293725
SNYK-JS-WEBPACKDEVSERVER-10300777
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Link Resolution Before File Access ('Link Following')
Summary by Sourcery
Upgrade @backstage/plugin-azure-devops-common to version 0.0.1 to resolve security vulnerabilities.
Bug Fixes:
Chores: